View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000794T99X171.00 SKB EagleSW Issuepublic2019-11-26 10:222020-08-11 15:45
Reporter(SW) Jason LingAssigned To(SW) Jason LingDue Date
PrioritynormalSeveritys2-severeReproducibilityalways
Status closedResolutionfixed 
Summary0000794: The behavior of Notification indicator does not meet requirement.
DescriptionHi Mr. Jason Park,

Our QA report one issue to us about the behavior of notification indicator.

According to the document "Custom Launcher requirement" on ATV Help. (Please check requirement.jpg)

The indicator MUST distinguish between unseen notications, seen (but not dismissed) notications, and no notications.

We have checked Android Standard Launcher
Step 1. The system receives new a notification, the number of the indicator increases by 1 and the background color turns to blue. (Please check unseen.png)
Step 2. The User presses the indicator and then does not remove any information, then presses back key. The number of indicator remains the same, but the background color of indicator becomes transparent (Please check seen.png)

The indicator of Android Standard Launcher can distinguish between unseen notications and seen, but we can not distinguish between these 2 states on SKB's Launcher.

Could you check this issue with the owner?
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (ALTech) Jason Park , (ALTech) Juyoung Park , (ALTech) SY Yoon

Activities

(SW) Jason Ling

2019-11-26 10:22

developer  

requirement.jpg (54,844 bytes)   
requirement.jpg (54,844 bytes)   
unseen.png (150,477 bytes)   
unseen.png (150,477 bytes)   
seen.png (150,827 bytes)   
seen.png (150,827 bytes)   

(ALTech) SY Yoon

2019-11-27 13:42

developer   ~0003215

Last edited: 2019-11-27 13:43

 Hi Jason Ling,

I have quesion about it.
How does your QA Team know about it ?
Did your QA Team find this issue in other project ?
Do you think it cannot waive by Google ?

We have new SW for new UI. And SKB QA started to test this SW from this week.
So it may impact to project schedule.
So we should know on this issue to explain to SKB.

(SW) Jason Ling

2019-11-27 14:34

developer   ~0003216

Hi Mr. Yoon,

Our QA find this issue on other project, so they verified it again on BFX-AT100.

The test item related to indicator on Smoke Test is
"Verify the notification indicator is dynamically changed (i.e connect/disconnect USB stick, connect/disconnect ETH cable or Wi-Fi, Google accont log in/out, etc)"
so I guess that 3PL just verified the number of indicator can change or not in previous MR.

I can't guarantee how 3PL will test this item next MR, so I just let you know that the behavior of indicator does not meet the requirement.

(ALTech) Jason Park

2019-12-03 14:26

developer   ~0003225

hi Jason

although we gave information to SKB, until now we don't receive any feedback.
if it have some update, I will update it .

Thanks.

(SW) Jason Ling

2020-01-09 08:47

developer   ~0003277

Hi Mr. Jason Park,
Any Update?

(ALTech) Jason Park

2020-01-09 11:58

developer   ~0003278

hi Jason

sorry to feedback today.
I talked it to SKB Manager in today meeting.
They also need a time more internally.
it can't include it in v15.513.9 version this week.

Thanks

(SW) Jason Ling

2020-07-08 20:04

developer   ~0003733

Hi Mr. Jason Park,

This issue has not been fix in UI 5.2.0.

As far as I know, Google TAM is more rigorous in SW reviewing from this year. And we can not use tight project schedule to get one time waiver.
I also know that some of Korean Google TAM use Smart3 in their home.
Please face up to this problem and ask UI vendor to fix it asap.

(ALTech) Jason Park

2020-08-11 15:20

developer   ~0004001

hi Jason.liang

Please check it in v15.520.8. if you confirm it, i will close it.

Thanks.

(SW) Jason Ling

2020-08-11 15:45

developer   ~0004005

Confirmed.

Issue History

Date Modified Username Field Change
2019-11-26 10:22 (SW) Jason Ling New Issue
2019-11-26 10:22 (SW) Jason Ling Status new => assigned
2019-11-26 10:22 (SW) Jason Ling Assigned To => (ALTech) Jason Park
2019-11-26 10:22 (SW) Jason Ling File Added: requirement.jpg
2019-11-26 10:22 (SW) Jason Ling File Added: unseen.png
2019-11-26 10:22 (SW) Jason Ling File Added: seen.png
2019-11-26 10:33 (SW) Jason Ling Description Updated
2019-11-27 12:22 (ALTech) Jason Park Issue Monitored: (ALTech) SY Yoon
2019-11-27 12:22 (ALTech) Jason Park Issue Monitored: (ALTech) Juyoung Park
2019-11-27 13:42 (ALTech) SY Yoon Note Added: 0003215
2019-11-27 13:43 (ALTech) SY Yoon Note Edited: 0003215
2019-11-27 14:34 (SW) Jason Ling Note Added: 0003216
2019-12-03 14:26 (ALTech) Jason Park Note Added: 0003225
2019-12-27 15:49 (ALTech) Jason Park Issue Monitored: (ALTech) Jason Park
2020-01-09 08:47 (SW) Jason Ling Note Added: 0003277
2020-01-09 11:58 (ALTech) Jason Park Note Added: 0003278
2020-07-08 20:04 (SW) Jason Ling Note Added: 0003733
2020-08-11 15:20 (ALTech) Jason Park Note Added: 0004001
2020-08-11 15:20 (ALTech) Jason Park Assigned To (ALTech) Jason Park => (SW) Jason Ling
2020-08-11 15:45 (SW) Jason Ling Note Added: 0004005
2020-08-11 15:45 (SW) Jason Ling Status assigned => closed
2020-08-11 15:45 (SW) Jason Ling Resolution open => fixed